VisualApplets
Operator Reference

The first 5 states are defined by the CXP standard for the PoCXP state machine. The last state ADC_Chip_Error represents an error when the communication between the FPGA and ADC chip is broken, which measures the voltage and current of the channel.

Current flowing through the CXP cable in mA.

Voltage sourced through the CXP cable in V.

State of the power over CXP engine. YES means the power controller will source the camera which requires power over CXP cable when connected, NO means the camera is not powered via the CXP cable. Note that this parameter is not showing whether the camera is sourced or not, instead it is showing that the capability of powering the camera via the CXP cable is enabled or not.

Frame grabber port to which the corresponding CXP channel is connected.

The firmware CXP channel which is currently monitored by the module. Note that there is not necessarily a one-by-one mapping between firmware port (resource CameraPort) and frame grabber port (physical connector). Instead it can be any permutation. The software discovery process reorders the channels and ports to achieve correct virtual interconnect.

Number of measured symbols received by the channel transceiver, which are not in 8b10b encoding or/and have wrong disparity.

This parameter shows whether the channel transceiver found the byte boundaries or not, so decoding the of 8b10b input stream can be performed.

This parameter shows the bit rate of the channel in Gb/s which is currently configured in the transceiver by the runtime discovery software.

This parameter shows the supported maximum stream packet size, which will be written also to the CXP camera during the CXP discovery step. The value is set by the firmware and complies with the CXP standard. This means the value must be divisible by 4 bytes because all packets are 32 bit aligned.

This parameter shows the version of the CXP standard which is currently in use.

This parameter counts the received trigger packets for which no acknowledgment could be sent, because the acknowledgment of the previous trigger was still ongoing. See CXP 2.0 standard, chapter 9.3.2. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts the trigger requests which were skipped, because the transmitter was still busy by sending the previous trigger packet. See CXP 2.0 standard, chapter 9.3.2. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs. If multiple trigger requests occur at the same time on parallel ports of a single CxpTxTrigger operator, the parameter might not count each skipped trigger. This can also happen if the requests occur within only a few clock cycles (e.g. < 10), which leads to multiple skipped trigger requests within a few clock cycles.

This parameter counts the situations in which a trigger packet was sent, but no acknowledgment packet was received for it yet and the timeout (480ns for 1-6Gb/s, 240ns for 10-12.5Gb/s) is reached. See CXP 2.0 standard, chapter 9.3.2. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts situations in which a GPIO packet was received but no acknowledgment could be sent, because the transmitter still was busy sending the acknowledgment of the previously received GPIO packet. See CXP 1.0 standard, chapter 8.3.3. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts GPIO requests which were skipped, because the transmitter was still busy by sending the previous GPIO packet. See CXP 1.0 standard, chapter 8.3.3. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts situations in which a GPIO packet was sent but no acknowledgment packet was received for it yet and the timeout (480ns for 1-6Gb/s, 240ns for 10-12.5Gb/s) is reached. See CXP 1.0 standard, chapter 8.3.3. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts situations in which a received stream packet is not correctly formatted, e.g. it misses the end of packet indicator etc. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts situations in which a control packet was sent but no acknowledgment packet was received for it yet and the timeout of 200 ms is reached. See CXP 2.0 standard, chapter 9.6.1.1. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts situations in which an acknowledgment for a control packet was received with a tag which is not matching the expected tag sent in the correspondent request control packet. See CXP 2.0 standard, chapter 9.6.1.2. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts situations in which an acknowledgment for a control packet was received which was not correctly formatted, e.g. it misses the end of packet indicator etc. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts situations in which another event packet is received but the corresponding acknowledgment can't be sent because the transmitter is still sending a previous event acknowledgment. See CXP standard 2.0, chapter 9.8.1.1. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts situations in which the received event packet is incomplete, e.g. it misses the end of the packet indicator. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts situations in which the received heart beat packet is incomplete, e.g. it misses the end of the packet indicator. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts situations in which the unknown packet data is received, which is not part of the CXP standard. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts errors received in packet headers and trailers which could be corrected. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter notifies whether errors were corrected in received trigger packets.

This parameter notifies whether errors were corrected in received trigger acknowledge packets.

This parameter notifies whether errors were corrected in received GPIO packets.

This parameter notifies whether errors were corrected in received GPIO acknowledge packets.

This parameter notifies whether errors were corrected in received stream packets.

This parameter notifies whether errors were corrected in received stream acknowledge packets.

This parameter notifies whether errors were corrected in received link test packets.

This parameter notifies whether errors were corrected in received event packets.

This parameter notifies whether errors were corrected in received heart beat packets.

This parameter counts errors received in packet headers and trailers which could not be corrected. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter notifies whether there were errors in received trigger packets which could not be corrected.

This parameter notifies whether there were errors in received trigger acknowledgement packets which could not be corrected.

This parameter notifies whether there were errors in received GPIO packets which could not be corrected.

This parameter notifies whether there were errors in received GPIO acknowledgement packets which could not be corrected.

This parameter notifies whether there were errors in received stream packets which could not be corrected.

This parameter notifies whether there were errors in received control acknowledgement packets which could not be corrected.

This parameter notifies whether there were errors in received link test packets which could not be corrected.

This parameter notifies whether there were errors in received event packets which could not be corrected.

This parameter notifies whether there were errors in received heart beat packets which could not be corrected.

This parameter counts CRC errors in received packets. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

Notify whether there were CRC errors in received stream packets.

This parameter notifies whether there were CRC errors in received control acknowledgement packets.

This parameter notifies whether there were CRC errors in received event packets.

This parameter counts received unsupported packets, i.e. those which are not allowed by CXP standard. For example event/heart beat packets in CXP 1.x or GPIO packets in CXP 2.0 and CXP 1.1.x. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter indicates whether a GPIO packet was received while using a CXP standard higher than 1.0.

This parameter indicates whether an event packet was received while using a CXP standard less than 2.0.

This parameter indicates whether a heart beat packet was received while using a CXP standard less than 2.0.

This parameter indicates whether a GPIO acknowledgment was received while using a CXP standard higher than 1.0.

This parameter indicates whether a GPIO request from VisualApplets was received while using a CXP standard higher than 1.0.

This parameter counts situations in which the length of the packet does not match the length defined in the packet header. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter indicated whether there is a length error in the stream packets.

This parameter indicated whether there is a length error in event packets.

This parameter counts tag errors in received event packets, which happens when the event packet tag got a gap. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.

This parameter counts the amount of received stream packets. Bits [29:0] count the number of packets. Bit [30] is set when a counter overflow occurs.

The heart beat period is defined in CXP 2.0 standard as 100ms maximum, i.e. within that time at least 1 heart beat packet needs to be send by the camera. This parameter counts the situations in which this condition is not met. Bits [11:0] count the amount of violations. Bit [12] is set when a counter overflow occurs.